azure-functions-durable/azure/durable_functions/internal/compat/history_projection.py:101

• TaskScheduledEvent and SubOrchestrationInstanceCreatedEvent are projected with a Name field (from the name dataclass field), while other projected events use the v1 FunctionName key (e.g., ExecutionStarted) and merged completion events also emit FunctionName. If an orchestration is still running and has scheduled-but-not-yet-completed work, these scheduled events will surface with Name, which is inconsistent with the rest of the v1 history shape and makes consumers handle two keys for the same concept.

    if isinstance(
            event,
            (history.TaskScheduledEvent,
             history.SubOrchestrationInstanceCreatedEvent)):
        item.pop("Version", None)

azure-functions-durable/azure/durable_functions/internal/compat/durable_orchestration_status.py:156

• The history property docstring says history is populated only when show_history=True is passed to get_status, but from_json() can also populate history when historyEvents / legacy history is present. This makes the doc misleading for callers who reconstruct a status from JSON.

    def history(self) -> Optional[list[Any]]:
        """Get the execution history.

        The history is populated only when requested by passing
        ``show_history=True`` to the client's compatibility ``get_status`` API.
        """

CHANGELOG.md:45

• Wrapped changelog bullet lines should not be indented; this entry is inconsistent with other wrapped bullets in this file (e.g., the next item continues at column 1).

- Failed task and sub-orchestration history events now retain the host-provided
  failure `reason` and redacted `details` alongside structured failure details.

azure-functions-durable/CHANGELOG.md:37

• Wrapped changelog bullet lines should not be indented; most wrapped bullets in this changelog continue at column 1 (for example, the next item’s continuation line starts with header.).

- The v1-compatible `get_status()` API now supports `show_history` and
  `show_history_output`, including compacted `historyEvents` output without an
  additional history request when history is not requested.

azure-functions-durable/azure/durable_functions/internal/compat/durable_orchestration_status.py:156

• The history property docstring is now inaccurate: history can also be populated when reconstructing a status via from_json() (it reads historyEvents/legacy history), not only via get_status(show_history=True). This can mislead callers relying on JSON round-trips.

        """Get the execution history.

        The history is populated only when requested by passing
        ``show_history=True`` to the client's compatibility ``get_status`` API.
        """

azure-functions-durable/azure/durable_functions/internal/compat/history_projection.py:145

• When compacting sub-orchestration events, the scheduled SubOrchestrationInstanceCreatedEvent entry is removed and its instance_id is not copied onto the corresponding *Completed/*Failed event. This drops InstanceId from the projected v1 historyEvents, making sub-orchestration entries harder to correlate with child instances and diverging from the v1 history shape (which includes the child instance id on these events).

    scheduled_index, scheduled_event = scheduled
    item["ScheduledTime"] = _format_datetime(scheduled_event.timestamp)
    item["FunctionName"] = scheduled_event.name
    if show_input and scheduled_event.input is not None:
        item["Input"] = scheduled_event.input
    removed_indexes.add(scheduled_index)